Purpose

This tool guide describes how to use SoDA to create a Software Architecture Document. SoDA automates the generation of the report so that it is created quickly and accurately. The Software Architecture Document can be generated by SoDA either with the Word or Frame versions of the product. SoDA collects architectural significant aspects from a Rose model and adds those into the Software Architecture Document. This will only work if the Rose model follows the structure and naming convention for the Rose model.

Related Rational Unified Process Artifact: Software Architecture Document

Overview

This Tool Mentor is applicable when running Windows NT 4.0 or UNIX.

To create a The Software Architecture Document using SoDA, choose one of the following options:

  1. Using SoDA/Word to generate a Software Architecture Document
  2. Using SoDA/Frame to generate a Software Architecture Document

1. Using SoDA/Word to generate a Software Architecture Document To top of page

  1. From Rose, in any context.
  2. Select Report=>SoDA Report.
  3. From the list of available reports, select Rational Unified Process Software Architecture Document. If you do not see that report, cancel and make sure you have a use case selected in your class diagram.
  4. Click OK.
  5. Review the generated report.

2. Using SoDA/Frame to generate a Software Architecture Document To top of page

  1. From Frame, select File=>New. Click on SoDA, then RoseTemplates, then RationalUnifiedProcessSoftwareArchitectureDocument.fm.
  2. Edit the Connector and enter the name of the model file and the name of the use case.
  3. Use File=>Save As to save the template to a personal or project directory. You may wish to change the name of the template to reflect the name of the use case, such as ConductTransactionsReport.doc
  4. Select SoDA=>Generate Document.
  5. Review the generated document.

The next time you want to generate this same document, simply open the document and select SoDA=>Generate Document

3. Structure and naming convention for the Rose model To top of page

Example structure of the Rose model. The following diagrams are extracted from the Rose model by the SoDA template and presented in the appropriate sections of the Software Architecture Document:
  • The use cases and actors which are considered to be 'architecturally significant' should be depicted in the diagram 'Architecturally Significant Use Cases'. They will be presented in the Use-Case View section of the Software Architecture Document.
  • The classes, interfaces, packages and subsystems which are considered to be 'architecturally significant' should be depicted in the diagram 'Architecturally Significant Model Elements'. They will be presented in the Logical View section of the Software Architecture Document.
  • The packages which represent layers in the design model should be depicted (along with any package dependencies) in the diagram 'Architecture Overview - Package and Subsystem Layering'. They will be presented in the Logical View section of the Software Architecture Document.
  • Any diagram in the 'Process View' package will be presented in the Process View section of the Software Architecture Document.
  • Any diagram in the 'Implementation Model' package will be presented in the section of the same name in the Software Architecture Document.
  • Any diagram in the 'Deployment View' will be present in the Software Architecture Document section of the same name.

 

Copyright  ⌐ 1987 - 2000 Rational Software Corporation

Display Rational Unified Process using frames

Rational Unified Process